home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d7
/
hostplus.arc
/
README.DOC
< prev
next >
Wrap
Text File
|
1990-04-22
|
6KB
|
131 lines
HELLO
-----
I neither work for Exis, nor do I hold stock in that company. Nor I am
requesting financial renumeration for the enclosed files. With that
concept established, I can honestly say that you are probably using one
of the best (if not the best) telecommunications application program
available.
One of the reasons Telix is such a good application program is because
of the versitility afforded you, the user. The enclosed files (except
for SYNC.MSG) are designed to be compiled with Telix's Salt compiler
and, hopefully, offer enhancements to the scripts you may presently be
using.
In the future, I plan to add color to the host script file's capabilities,
multiple upload and download directories, individual passwords, individual
access levels, and who knows, maybe a front end mailer/message packer.
If you have any suggestions, please send a note via The Marshfield Exchange
1:152/18 or, The Empire Builder 1:152/32
Contributions are not requested but will be glady accepted. If you wish
to thank me with a contribution then please keep it under $10,000 <GRIN>.
Lawrence Stone
Lawrence Stone Research Group (LSRGroup)
P.O. Box 5715
Charleston, OR 97420
FILES LIST
----- ----
This archive contains script files for the Salt compiler used
by the Telix communications program from Exis, Inc.
Files included within this archive are:
LSRHOST.SLT An improved host script
PUMAUP.SLT An upload script for Puma protocol
PUMADOWN.SLT A download script for Puma protocol
README.DOC This document.
SYNC.MSG An ASCII file used with LSRHOST.SLT
PUMA
----
Two files are included for using Telix with the external transfer
protocol, Puma. These scripts are PUMAUP.SLT and PUMADOWN.SLT.
Compile these with the Salt compiler by issuing the command:
CS pumaup
CS pumadown
To use these with Telix, you must inform Telix to use the PUMAUP
file for Puma uploads and PUMADOWN for Puma downloads. Refer to
your Telix manual for more details on using external protocols.
LSRHOST
-------
This version of the Telix Host Script File has been modified by:
Lawrence Stone, Lawrence Stone Research Group, April, 1990. It
has been named as LSRHOST.SLT so as not to confuse it with the
original host script. You can rename it to anything you wish,
including HOST.SLT, if you desire.
Note: All modifications by me can be found in the LSRHOST script by
searching it for the initials, "LSR".
The following modifications are changes to the original Host Script
file, as found in this version of LSRHOST:
1. Requires level II password before caller can access the
shell command. Shell still needs separate password.
2. Requires level II password before caller can access the
shut down host command. Still requires separate password.
3. The do_one_caller routine would erroneously trap ARQ modems
in the if expression, "if (!determine_baud())". This was
corrected by adding {} symbols below the if statement. The
original expression failed to work because there wasn't any
command immediately below the if expression, only a remark
to "do something here if this is a problem" (at least in my
first copy of the host script). The {} symbols properly define
the limits of this if expression.
4. When the caller shells to DOS, the original script would
write a batch file to control the shell, call DOS to
execute the batch, then, upon return to the program, close
the file just written to. Because the file was left open,
Telix could not run it - the batch file must be closed first!
Therefore, this script properly closes the file prior to
having DOS run the batch. (Note that new releases of Telix
have corrected this error.)
5. I discovered that if high speed, ARQ modems (HST, dual standard,
etc.) are calling a non-hand shaking modem (like my 2400 baud)
then, binary characters would dump into the current_caller
string. Worse, although you would see these characters from
the host computer, the caller would not see anything, just a
blinking cursor. I corrected the script to work with ARQ modems
by adding the command, type_file("SYNC.MSG") <included with this
script> and by increasing the initial delay from 1/10 second to
five seconds. The SYNC.MSG file forces high speed modems to
synchronize on it's text <ie, a substitute for a handshake> and
the increase in delay time allows high speed modems to settle in.
Note that callers using ARQ modems will *not* see the SYNC.MSG on
their consoles but, non-ARQ callers *will* see this message!
These changes are found in the do_one_caller routine.
6. Added dooR option to menu. This option requires that the user
creates a batch file called, RSHELL.BAT to run the door program.
It also requires level 2 password to access.
7. Added automatic log enteries to the host log as soon as a
call is received, and when ever a caller types any password,
or tries to go to a DOS shell, or returns from a DOS shell,
or tries to shut down the host mode. Also logs when user
enters or exits chat mode, lists any file, types any file, or
attempts to access the door. Each call received is now seper-
ated by a 47 character string of "=" symbols. This allows easy
recognition of each call received while listing the log.
8. Added PUMA external transfer protocal. Added automatic log
enteries whenever the user starts and ends Puma transfers.